Skip to content

ci: use GH_TOKEN for release-chain workflows#51

Merged
mattapperson merged 1 commit into
mainfrom
sdk-bot/release-automation-gh-token
Jun 3, 2026
Merged

ci: use GH_TOKEN for release-chain workflows#51
mattapperson merged 1 commit into
mainfrom
sdk-bot/release-automation-gh-token

Conversation

@mattapperson

Copy link
Copy Markdown
Collaborator

Use GH_TOKEN for the release-chain workflows

Follow-up to #49 (which merged before this rewire landed). Switches the
release-chain workflows on this repo from SUBTREE_PUSH_PAT to the dedicated
GH_TOKEN PAT now configured as a repo secret.

What changes

  • bump-openrouter-sdk.yaml — checkout token:, the bump-step GH_TOKEN,
    the open-PR GH_TOKEN, and the gate-step GH_TOKEN all now read
    secrets.GH_TOKEN. (Still a PAT, not the Actions GITHUB_TOKEN, so the
    opened bump PR triggers Perry + CI.)
  • publish.yaml — the openrouter-agent-published dispatch to
    openrouter-web now uses secrets.GH_TOKEN.

Secret requirement

  • GH_TOKEN — set on this repo. For the publish.yaml dispatch to be
    accepted, this PAT must have contents: write on
    OpenRouterTeam/openrouter-web
    (the dispatch target), plus
    contents+pull_requests: write here.

Verified with actionlint (clean); no SUBTREE_PUSH_PAT references remain.

[sdk-bot]

Switch the release-chain workflows from SUBTREE_PUSH_PAT to the dedicated
GH_TOKEN PAT now configured on this repo. Follows up the merged #49, which
landed before this rewire.
@mattapperson mattapperson merged commit 839b381 into main Jun 3, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant